Microsoft(R) Professional Toolkit for
               Visual Basic (TM) 1.0 Setup by Batch File
               -----------------------------------------

We recommend that you run TKSETUP.BAT from an MS-DOS(R) boot, not in a
shell from Microsoft Windows(TM). TKSetup must be run from MS-DOS and
from the drive in which you inserted the disk. For example, the
following won't work:

   C:\> a:tksetup

Instead, you must make drive A (or the drive in which you inserted the
disk) the active drive before running TKSetup:

   C:\> a:
   A:\> tksetup

When you run TKSetup as shown above (with no arguments), further usage
instructions will display on the screen.

TKSetup will work only with 5.25-inch 1.2 MB or 3.5-inch 1.44 MB
disks. TKSetup will not work with 5.25-inch 360K or 3.5-inch 720K
disks.

The Windows-hosted Setup program that this batch file replaces places
all VBX files associated with the custom controls in the
\WINDOWS\SYSTEM directory and gives you the choice of placing
duplicates in a \VBX subdirectory.

TKSetup automatically places the VBX files in the \VBX subdirectory.
We recommend that you either copy them into your \WINDOWS\SYSTEM
directory or make sure the \VBX directory is in your MS-DOS path. For
speed, it is better to place the VBX files in the \WINDOWS\SYSTEM
directory because Windows looks first in the \WINDOWS directory, then
in \WINDOWS\SYSTEM, then in the current directory, and finally in the
MS-DOS path for files.

  NOTE: The file VB.LIC *MUST* be present in your \WINDOWS\SYSTEM
  directory for you to successfully load any custom controls into the
  Visual Basic environment.

  ALSO NOTE: If you have Windows version 3.1 already installed, the
  COMMDLG.DLL file that comes with Windows 3.1 is the most current. It
  is date/time stamped 3/10/92 3:10 A.M. Regardless of the date/time
  stamp on the Professional Toolkit's version, use the version that
  comes with 3.1. If you have not yet upgraded, COMMDLG.DLL is
  provided to allow the use of the CMDialog custom control. If you do
  have 3.1 installed, don't copy COMMDLG.DLL to your \WINDOWS\SYSTEM
  directory with all the other files (VBXs).

If at a later time you upgrade to 3.1, the Windows Setup program will
correctly write the most current version of the DLL into the
\WINDOWS\SYSTEM directory. In either case, this will not affect the
use of the CMDialog.VBX custom control.

The batch file also copies four files to the root of the chosen
directory:

   TKSETUP.BAT
   TKSETUP1.BAT
   README.TXT (the file you are now reading)
   DECOMP.EXE

Upon successful completion of the setup, you can delete these files
from your hard disk, if you want.

  NOTE: TKSetup will not install the multimedia driver files stored in
  the root of Disk 1. Those files are compressed in a different format
  and are installed by using the Drivers icon in Windows 3.1 Control
  Panel, or by using the multimedia extensions driver installation
  option.

INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY
ACCOMPANY THIS DOCUMENT (collectively referred to as an Application
Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE.
The user assumes the entire risk as to the accuracy and the use of
this Application Note. This Application Note may be copied and
distributed subject to the following conditions: 1) All text must be
copied without modification and all pages must be included; 2) If
software is included, all files on the disk(s) must be copied to high-
density disks without modification (the MS-DOS(R) utility DISKCOPY is
appropriate for this purpose); 3) All components of this Application
Note must be distributed together; and 4) This Application Note may
not be distributed for profit.

Copyright (C) 1992 Microsoft Corporation. All Rights Reserved.
Microsoft and MS-DOS are registered trademarks and Windows and Basic
are trademarks of Microsoft Corporation.